@chorlton2080 Solved: I discovered the USB cable I was using did not have the data connections wired, must be for fast charging only.

It's the controllers fault. Open it up and clean the button contact pads.

@stheodore83 Please do not post a support request without first reading and following the advice in https://retropie.org.uk/forum/topic/3/read-this-first

@edmaul69 I was actually able to get it to work. I tried a different ps3controller option, Shanwan Clone, and both controllers immediately connected. Problem solved, hooray!

edit: This also seems to have solved my Bluetooth reconnect issues as well. If anybody else is having the issues that I was, I suggest trying a few of the other ps3bluetooth driver options.

thanks, but problem persist. When I install the ps3 controller driver, the onboard bluetooth of the pi3 stops working and when I remove it works again.

when doing "sudo service bluetooth status" I get the following:

pi@retropie:~ $ sudo service bluetooth status

● bluetooth.service - Bluetooth service
Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled)
Active: failed (Result: signal) since Tue 2017-06-13 00:05:01 UTC; 5min ago
Docs: man:bluetoothd(8)
Main PID: 767 (code=killed, signal=KILL)
Status: "Running"

Jun 12 02:17:08 retropie bluetoothd[767]: Bluetooth daemon 5.23
Jun 12 02:17:08 retropie systemd[1]: Started Bluetooth service.
Jun 12 02:17:08 retropie bluetoothd[767]: Starting SDP server
Jun 12 02:17:08 retropie bluetoothd[767]: Bluetooth management interface 1.1...d
Jun 12 02:17:08 retropie bluetoothd[767]: Sap driver initialization failed.
Jun 12 02:17:08 retropie bluetoothd[767]: sap-server: Operation not permitte...)
Jun 13 00:05:01 retropie systemd[1]: bluetooth.service: main process exited...LL
Jun 13 00:05:01 retropie systemd[1]: Unit bluetooth.service entered failed ...e.
Hint: Some lines were ellipsized, use -l to show in full.
pi@retropie:~ $

I gave up and just re-flashed Retropie. It's working fine again.

Welcome to the RetroPie Forums!

I would personally get another controller (like a real one).
Can we also see a picture of the PS3 controller? It could be real, it could be fake and possibly RetroPie is assuming something else.

Should work, just depends if the pi recognizes it as a ps3 controller.

@AlexMurphy Thanks!

@r641wd I don't have enough information from your description to suggest next steps.

Searching for the error you described on Google seems to take me to this page. See if those steps help?

Did you follow the setup exactly? Also have you rebooted since you paired? If you have did you update you rc.local to include sixad --start & ?

@PET2001
Oh, they look very much alike... i will give it a harder go, tonight and thanks for your detailed 'how to'. I refuse to give up :)

Thanks man!!

@bshogeman said in Hotkeys such as select+start don't work any more.:

I must not touch the menu item retropie -> retroarch. Don't update anything within that app.

To be more precise about the danger of this "app": Do NOT enable "Save Configuration on Exit".

Can anyone tell me what files to delete, replace, recover to fix this problem without reinstalling everything again?

Look for the retroarch.cfg.rp-dist files and replace the retroarch.cfg files with those.

Example:

mv /opt/retropie/configs/all/retroarch.cfg.rp-dist /opt/retropie/configs/all/retroarch.cfg mv /opt/retropie/configs/nes/retroarch.cfg.rp-dist /opt/retropie/configs/nes/retroarch.cfg mv /opt/retropie/configs/snes/retroarch.cfg.rp-dist /opt/retropie/configs/snes/retroarch.cfg # repeat it for other systems

More info about this kind of issue here and here.

The ghost controller is most likely your keyboard. I have the exact same experience here. You could try removing the USB dongle for the keyboard, reboot and see if the PS3 pads are detected as 1 and 2.

It was an issue for me because the PSX emu would not let me play, since the player1 controller was 'occupied', but i got around this by changing some config file, so controller 2 for player 1 and controller 3 is for player 2. Unfortunately i can't remember which config file it was. I am sure that someone would have this on the tip of their tongue.

I tried to remove the USB dongle for the mouse/keyboard today, and it resulted in a lot longer playing time before freeze. This freeze issue is definitely related to controller hookup!

I have had a weird experience 2 times... i let the frozen screen hang, and after a good while, the game resumes ?!?! Well, the controller connection is lost, even though the controller LEDs are still lit. If i turn off the controllers and turnthem back on again, they won't pair wih bluetooth.

But it means that i can maybe pull some log files - I'm just not experienced enough to know which logfile woud be relevant, and how to pull it. Maybe someone could help me out in this regard??

@mitu ok thank you

Hi @BuZz ,

Yes you're entirely right,I will ask over there as well.